home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
onerun33.zip
/
ONERUN.DOC
< prev
next >
Wrap
Text File
|
1992-11-27
|
11KB
|
280 lines
============================
OneRun!
============================
(c)1990,91,92 T&J Software
One of the T&J Software Collection of multi-BBS door programs.
Supporting PCBoard, Wildcat!, Gap, QBBS, RBBS, Spitfire,
UltraBBS, Telegard, TriBBS, Remote Access, and WWIV
VERSION 3.3 11/27/92
By
Tom Wildoner
397 West Broadway
Jim Thorpe, PA
18229
VOICE (717)325-9480
*between 5:30 & 10:00 p.m. Eastern Time
From
The T&J BBS
(717)325-9481
1200/2400/9600/19200/38400
24 Hours/Day
LEGALITIES:
THIS SOFTWARE AND ACCOMPANYING MATERIALS ARE DISTRIBUTED "AS IS" WITHOUT
WARRANTY, EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL ANYONE INVOLVED WITH THE CREATION AND PRODUCTION OF THIS
PRODUCT BE LIABLE FOR INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES, ARISING
OUT OF ANY USE THEREOF OR BREACH OF ANY WARRANTY.
DISTRIBUTION:
You may make this file available for downloading from your BBS or you may
upload it to any BBS of your choice, provided that you do not make any
changes to the contents of the archive (ZIP file). The archive and its
individual contents may not be used by any service that charges any money
whatsoever, without the written permission of the author.
PROGRAM DESCRIPTION:
====================
ONERUN was made to help compliment other T&J Software doors games and
future utility programs. It allows you, the SysOp, to set up door games
or other door programs for limited access during the day.
ONERUN creates a small player record file which contains the players name,
date, and number or plays during that day. This file is checked during
each play and the number of plays is adjusted. If you say the player can
only enter your door twice per day, OneRun will only allow him to enter
twice per day.
CONFIGURATION:
=============
Example configuration file for PCBOARD.SYS
------------------------------------------
C:\PCB\PCBOARD.SYS <=- (Full pathname of your PCBOARD.SYS file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
Example configuration file for USERS.SYS
----------------------------------------
C:\PCB\USERS.SYS <=- (Full pathname of your USERS.SYS file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
Example configuration file for DOOR.SYS
---------------------------------------
C:\BBS\DOOR.SYS <=- (Full pathname of your DOOR.SYS file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
Example configuration file for USERINFO.DAT
-------------------------------------------
C:\BBS\USERINFO.DAT <=- (Full pathname of your USERINFO.DAT file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
NOTE: DOOR.SYS must be in the SAME directory as USERINFO.DAT
Example configuration file for CALLINFO.BBS
-------------------------------------------
C:\BBS\CALLINFO.BBS <=- (Full pathname of your CALLINFO.BBS file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
Example configuration file for DORINFOx.DEF
-------------------------------------------
C:\BBS\DORINFOx.DEF <=- (Full pathname of your DORINFOx.DEF file
where 'x' is the BBS Node number.
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
Example configuration file for SFDOORS.DAT
------------------------------------------
C:\BBS\SFDOORS.DAT <=- (Full pathname of your SFDOORS.DAT file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
Example configuration file for CHAIN.TXT
----------------------------------------
C:\BBS\CHAIN.TXT <=- (Full pathname of your CHAIN.TXT file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
Example configuration file for GTUSER.BBS
-----------------------------------------
C:\BBS\GTUSER.BBS <=- (Full pathname of your GTUSER.BBS file)
T&J Software <=- (Change this to your BBS name)
Tom <=- (The Sysop's first name)
Wildoner <=- (The Sysop's last name)
1 <=- (COM port number - defaults to 1)
1 <=- (Node number - defaults to 1)
This Door is multi-node compatible so you may run more than 1 node from
the same .CFG file provided the path to your system file (DORINFOx.DEF,
CALLINFO.BBS, etc) is exactly the same unless you are using environment
variables, (q.v.)
Environment Variables
=====================
PCBoard automatically creates the %PCBDRIVE% & %PCBDIR% environment
variables. Non-PCBoard systems may also use these variables by including
the following in either your BBS batch or AUTOEXEC.BAT
SET PCBDRIVE=C: <- Drive letter of your BBS files
SET PCBDIR=\BBSDIR <- Path to your BBS files
Then in your Door .CFG file instead of putting C:\BBSDIR\DOOR.SYS, you
would put %PCBDRIVE%%PCBDIR%\DOOR.SYS. This allows you to use just one
.CFG file for multi-node operation!
To specify a non-standard IRQ, put the IRQ number after the .CFG on the
command line. For example:
ONERUN ONERUN.CFG /5
or using the PCBDRIVE procedure: SET IRQ=5 and use
ONERUN ONERUN.CFG /%IRQ%
This tells the program to use IRQ 5 instead of the standard IRQ.
Had reports of conflicts when using non-standard IRQ's on Novell/Netware
systems. Seems Novell also uses the / character so something went screwy
somewhere. So I added the * (asterisk) which may be used instead of the /
in case of a conflict. In other words, /%IRQ% and *%IRQ% will both work
and are interchangeable.
When specifying the location of the system file on line 1 of the doors .CFG
file, you may use the environment variables %pcbdrive%, %pcbdir%, %pcbnode%,
and %wcnodeid%. Some examples:
PCBoard:
USERS.SYS in C:\PCB - %pcbdrive%%pcbdir%\USERS.SYS
USERS.SYS in C:\PCB\NODE1 - %pcbdrive%%pcbdir%\NODE%pcbnode%\USERS.SYS
Wildcat!:
USERINFO.DAT in C:\WC\NODE1 - C:\WC\NODE%wcnodeid%
Non-PCBoard systems may use the PCB environment variables by setting them
in either AUTOEXEC.BAT or in the batch that runs the door. For example:
SET PCBDRIVE=C:
SET PCBDIR=\BBSDIR
SET PCBNODE=1
Fossil Driver Support
---------------------
DoorFrame supports the use of Fossil drivers. To tell your Door to use the
Fossil driver instead of the standard COM ports, just put /FD on the command
line when running the door. For example:
MYDOOR MYDOOR.CFG /FD
indicates that a Fossil driver is present and should be used. If no Fossil
driver is detected, DoorFrame will print a message to that effect and exit
the door gracefully.
Sysop Keys
==========
F3 - Toggles the printer On/Off. Value is passed to PCBoard and/or
written to DOOR.SYS and USERS.SYS
F4 - Toggles the Page Bell on/off. Value is passed to PCBoard
and/or written to DOOR.SYS and USERS.SYS
F5 - DOS Shell. Allows SysOp to exit to DOS from inside a DOOR.
F7 - Toggles the Caller Alarm On/Off. Value is passed to PCBoard
and/or written to DOOR.SYS and USERS.SYS
F8 - Returns the caller involuntarily to the BBS.
F9 - Toggles the local display On/Off. Value is passed to PCBoard
and/or written to DOOR.SYS and USERS.SYS
F10 - Activates SysOp CHAT mode within the DOOR.
ESC - Deactivates CHAT mode. DOOR is resumed.
UP - Give the caller extra time while in the DOOR.
DN - Subtract time from the caller while in the DOOR.
HOME - HELP key for Status Line options.
ALT-N - SysOp next on toggle. Value passed to PCBoard. (PCBoard only)
ALT-X - PCBoard will exit after current caller logs off. Value is
passed to PCBoard. Not available on non-PCBoard systems.
ONERUN.SYS
1 'How many plays per day per player.
"01-20-1992" 'The current date in this format "MM-DD-YYYY"
ONERUN.DAT -- One run will take care of this file. It's listed here
so you will know what it contains.
1 'Number of user records.
"Nobody","01-20-1992",0 'Starting user record.
How to configure your DOORx.BAT files:
CD\WC30\DOOR\LEMON
ONERUN ONERUN.CFG
IF EXIST ONE.RUN GOTO QUIT
LEMON20 LEMON.CFG
:QUIT
DEL ONE.RUN
CD\WC30
LINE 1: Path to your door directory.
LINE 2: Run your ONERUN program.
LINE 3: This line is very important. ONERUN creates the file ONE.RUN
if the user has no more access to the door. This line causes
the batch file to skip the actual door program if the file
ONE.RUN was found in the directory.
LINE 4: Your actual door program (however many lines it takes).
LINE 5: Line that the batch file will branch to if ONE.RUN is
found to exist.
LINE 6: Delete the old ONE.RUN file.
LINE 7: Return to the BBS.
To run in LOCAL mode simply enter: ONERUN LOCAL
FUTURE VERSIONS:
================
--->> Let me know what you would like to see!
REGISTERING:
============
That's all there is to it! If you have any problems or questions
please feel free to call the T&J BBS at (717)325-9481 and join the
T&J Software Conference. Online ordering using Mastercard or Visa
is available at the T&J Software BBS!
BENEFITS OF REGISTERING:
========================
OneRun will normally allow you to specify how many plays per day a
user can play the actual door. This unregistered version defaults to
1 (line 1 of the ONERUN.SYS file). Registering will allow you to set this
number to anything you wish.
See the REGISTER.TXT file for information on registering!